Fuel-economy optimization for autonomous driving systems

ABSTRACT

A method includes identifying route data including a threshold arrival time for a route for an autonomous vehicle (AV) and calculating, based on the route data and a fuel-efficient speed value for each segment of the route, an estimated arrival time. Responsive to the estimated arrival time not meeting the threshold arrival time, the method includes identifying at least a subset of segments that each represent a candidate for speed increase, computing, for each segment in the subset and based on the fuel economy data, a correlation metric that indicates a correlation between a change in fuel economy and a change in speed for a corresponding segment in the subset, and increasing, for at least one segment from the subset and based on a respective correlation metric, a fuel-efficient speed value of the corresponding segment from the subset to provide a speed profile reflecting the increased fuel-efficient speed value.

TECHNICAL FIELD

The instant specification generally relates to autonomous vehicles. Morespecifically, the instant specification relates to implementingfuel-economy optimization with respect to the autonomous vehicles.

BACKGROUND

An autonomous vehicle (AV) operates by sensing an outside environmentwith various sensors and charting a driving path through the environmentbased on the sensed data, Global Positioning System (GPS) data, and roadmap data. Among the autonomous vehicles are trucks used forlong-distance load deliveries. The trucking industry is sensitive tovarious costs and, in particular, fuel costs. To improve fuelefficiency, human truck drivers use a variety of driving techniques,such as maintaining a constant speed whenever possible, acceleratingthrough downhill sections of the road in order to acquire an additionalmomentum to carry the vehicle into subsequent uphill sections, and othertechniques, which can be equally useful for autonomous vehicles.Successful implementation of such methods, however, can depend on theroad conditions. Higher efficiency is usually achieved when traffic islight. Conversely, presence of a large number of other trucks, carryingdifferent loads and moving with different speeds, as well as passengercars, motorhomes, and other vehicles is often detrimental to drivingperformance. Challenging weather conditions can introduce furtheruncertainty and increase costs while negatively affecting expecteddelivery times.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure is illustrated by way of examples, and not by way oflimitation, and can be more fully understood with references to thefollowing detailed description when considered in connection with thefigures, in which:

FIG. 1 is a diagram illustrating components of an example architectureof a system that provides fuel-economy optimization for an autonomousvehicle (AV), in accordance with some implementations of the disclosure.

FIG. 2 is a diagram illustrating components of an example architectureof a system and example data flows pertaining to fuel-economyoptimization, in accordance with some implementations of the disclosure.

FIG. 3 depicts a flow diagram of an example method of performingfuel-economy optimization, in accordance with some implementations ofthe disclosure.

FIG. 4 depicts a block diagram of an example computer device withinwhich a set of instructions, for causing the machine to perform any ofthe one or more methodologies discussed herein can be executed, inaccordance with some implementations of the disclosure.

SUMMARY

In one implementation, disclosed is a method including identifying routedata for a route for an autonomous vehicle (AV). The route data includesa threshold arrival time. The method further includes determining, by aprocessing device based on fuel economy data associated with the AV, afuel-efficient speed value for each of a plurality of segments of theroute. The method further includes calculating, based on the route dataand the fuel-efficient speed value for each of the plurality of segmentsof the route, an estimated arrival time. Responsive to the estimatedarrival time not meeting the threshold arrival time, the method furtherincludes identifying, among the plurality of segments, at least a subsetof segments that each represent a candidate for speed increase,computing, for each segment in the subset and based on the fuel economydata, a correlation metric that indicates a correlation between a changein fuel economy and a change in speed for a corresponding segment in thesubset, and increasing, for at least one segment from the subset andbased on a respective correlation metric, a fuel-efficient speed valueof the corresponding segment from the subset to provide a speed profilereflecting the increased fuel-efficient speed value of the correspondingsegment. The AV is to travel along the route based on the speed profile.

In another implementation, disclosed is a system including a memorydevice and a processing device coupled to the memory device. Theprocessing device is to identify route data for a route for anautonomous vehicle (AV). The route data includes a threshold arrivaltime. The processing device is further to determine, based on fueleconomy data associated with the AV, a fuel-efficient speed value foreach of a plurality of segments of the route. The processing device isfurther to calculate, based on the route data and the fuel-efficientspeed value for each of the plurality of segments of the route, anestimated arrival time. Responsive to the estimated arrival time notmeeting the threshold arrival time, the processing device is further toidentify, among the plurality of segments, at least a subset of segmentsthat each represent a candidate for speed increase, compute, for eachsegment in the subset and based on the fuel economy data, a correlationmetric that indicates a correlation between a change in fuel economy anda change in speed for a corresponding segment in the subset; andincrease, for at least one segment from the subset and based on arespective correlation metric, a fuel-efficient speed value of thecorresponding segment from the subset to provide a speed profilereflecting the increased fuel-efficient speed value of the correspondingsegment. The AV is to travel along the route based on the speed profile.

In another implementation, disclosed is a non-transitorycomputer-readable storage medium having instructions stored thereonthat, when executed by a processing device, cause the processing deviceto identify route data for a route for an autonomous vehicle (AV). Theroute data includes a threshold arrival time. The processing device isfurther to determine, based on fuel economy data associated with the AV,a fuel-efficient speed value for each of a plurality of segments of theroute. The processing device is further to calculate, based on the routedata and the fuel-efficient speed value for each of the plurality ofsegments of the route, an estimated arrival time. Responsive to theestimated arrival time not meeting the threshold arrival time, theprocessing device is to identify, among the plurality of segments, atleast a subset of segments that each represent a candidate for speedincrease, compute, for each segment in the subset and based on the fueleconomy data, a correlation metric that indicates a correlation betweena change in fuel economy and a change in speed for a correspondingsegment in the subset, and increase, for at least one segment from thesubset and based on a respective correlation metric, a fuel-efficientspeed value of the corresponding segment from the subset to provide aspeed profile reflecting the increased fuel-efficient speed value of thecorresponding segment. The AV is to travel along the route based on thespeed profile.

DETAILED DESCRIPTION

A vehicle (e.g., truck) uses a significant amount of fuel. Fuel costsmay be a third of the total cost of operating trucks (e.g., commercialclass 8 trucks). At some portions of routes (e.g., uphill grade), avehicle consumes more fuel than other portions of the route (e.g., flator downhill grades, etc.).

Travel speed is one factor that can have a disproportionate impact onfuel economy. Fuel economy represents a measure of correspondence (e.g.,a ratio, percentage, etc.) between the amount of fuel (or other type ofenergy) consumed by a vehicle and distance traveled by the vehicle.Traveling slower may increase fuel economy. There are constraints onlower speed bounds, such as legal speed limits and arrival time windowsthat may cause a vehicle to travel faster than what is optimal. A legalspeed limit (also referred to herein as a regulatory speed limit) may bea maximum or minimum speed set for a given stretch of a road by arespective legislative body. Arrival time windows can include a time bywhich a vehicle is to arrive at a destination (e.g., cargo deliverydeadline), hours of service, avoiding travelling at certain times (e.g.,not driving at night), and/or the like. To meet the arrival time window,a vehicle may travel at faster-than-optimal speeds for differentportions of the route.

Conventionally, a vehicle travels at a set speed (e.g., via a cruisecontrol system) to meet an arrival time window (e.g., set cruise controlspeed at 60 miles per hour to arrive in one hour at a destination thatis 60 miles away). By using a set speed to travel along a route that hasvariations (e.g., differences in grade), a vehicle may have aless-than-optimal fuel economy. At some portions of the route (e.g.,uphill grades), the vehicle may have a worse fuel economy than otherportions of the route (e.g., flat or downhill grades).

Aspects of the disclosure address the above challenges along withothers, by generating a speed profile that includes verifiedfuel-efficient speed values for segments of a route for controlling anautonomous vehicle (AV). An AV performs vehicle actions, such asbraking, steering, and throttling, to move the AV from the startinglocation to the destination location along the route.

A processing device (e.g., hosted by a server or onboard the AV) canidentify route data including a threshold arrival time for a route ofthe AV. The threshold arrival time (e.g., arrival time window) caninclude a time by which the AV should arrive at a destination (e.g.,cargo delivery deadline), a maximum trip time and departure time, and/orthe like.

The processing device can determine, based on fuel economy dataassociated with the AV, a fuel-efficient speed value for each segment ofthe route. The fuel economy data can include input values and outputvalues. The input values can include speed values (e.g., miles per hour(mph)), grade values (e.g., uphill grade, downhill grade), total AV massvalues, wind values, and/or the like. The output values can include fueleconomy values (e.g., miles per gallon (mpg)) resulting from one or moreAVs driving based on the input values (e.g., fuel economy valuescollected from one or more AVs while driving at different speed values,etc.). For example, the fuel economy data may indicate that for a gradevalue of a segment of a route, total mass value of the AV, and ahistorical wind value of the segment, the greatest fuel economy value(e.g., highest mpg) may correspond to a fuel-efficient speed value of 30mph.

The processing device can verify whether the fuel-efficient speed valuefor each segment of the route corresponds to regulatory speed limits andtraffic data. As part of the verification, the processing device canupdate fuel-efficient speed values of the segments of the route ifneeded, and include the verified fuel-efficient speed values in thespeed profile. For example, if, based on the fuel economy data and inputvalues, the fuel-efficient speed value (e.g., speed value with thehighest mpg) for a segment is 20 mph, but the regulatory minimum speedlimit is 30 mph for the segment, the processing device can increase thefuel-efficient speed value from 20 mph to 30 mph for use in the speedprofile. In another example, if, based on the fuel economy data andinput values, the fuel-efficient speed value for a segment is 50 mph,but based on historical traffic data, the maximum threshold speed valuefor the segment is 40 mph, the processing device can decrease the fuelefficient speed value from 50 mph to 40 mph for use in the speedprofile.

The processing device can calculate, based on the route data and thecorresponding fuel-efficient speed value for each of the segments, anestimated arrival time. The estimated arrival time may be based on atotal travel time. The total travel time may be determined by addingtogether the segment travel time of each segment of the route. Thesegment travel time may be calculated by dividing a distance value ofeach segment by the fuel-efficient speed value for the segment (e.g., 30miles divided by 30 mph would equal 1 hour). The estimated arrival timemay also include buffer time.

The processing device can determine whether the estimated arrival timemeets the threshold arrival time. Responsive to the estimated arrivaltime not meeting the threshold arrival time, the processing device canidentify at least a subset of segments of the route that each representa candidate for speed increase (e.g., if the fuel-efficient speed valuefor the candidate segments does not meet a regulatory maximum speedlimit or a historical maximum speed value based on traffic data). Theprocessing device can compute, for each segment in the subset and basedon the fuel economy data, a correlation metric that indicates acorrelation between a change in fuel economy (e.g., change in mpg) and achange in speed (e.g., change in mph) for a corresponding segment in thesubset. For example, based on the fuel economy data, the processingdevice may determine that an increase of 1 mph for a segment generates adecrease of 2 mpg for the segment. The correlation metric may indicate a−2 mpg for +1 mph (e.g., −2 mpg/mph or −0.5 mph/mpg). Different segmentsof the route may have different correlation metrics (e.g., −3, −2, −1,0, etc. change in mpg per 1 mph increase). The processing device canincrease, for at least one segment from the subset and based on arespective correlation metric, a fuel-efficient speed value of acorresponding segment from the subset to provide a speed profilereflecting the increased fuel-efficient speed value for thecorresponding segment. For example, if different segments have adecrease of 3 mpg, decrease of 2 mpg, and decrease of 1 mpg for anincrease in 1 mph, the processing device may determine that the segmentwith the decrease of 1 mpg for an increase in 1 mph has the lowestdecrease in fuel economy. The processing device may then increase thefuel-efficient speed value for that segment to provide a speed profilereflecting the increased fuel-efficient speed value for that segment.The resulting speed profile can then be used by the AV to travel alongthe route.

Aspects and implementations disclosed herein provide numerous advantagesover existing technologies. By generating a speed profile that includesverified fuel-efficient speed values for controlling an AV along aroute, fuel consumption of the AV can be optimized while still allowingthe AV to arrive by the threshold arrival time. In some implementations,the speed profile can include additional information, such as acorresponding gear, braking system, etc. to use for each segment of theroute, to further improve fuel consumption and reduce wear and tear onthe AV. By improving fuel consumption, use of the speed profile canfurther result in less air pollution, while still meeting regulatoryspeed limits and threshold arrival times.

FIG. 1 is a diagram illustrating components of an example architecture100 of a system that provides fuel-economy optimization for anautonomous vehicle (AV) 101, in accordance with some implementations ofthe disclosure. In some implementations AV 101 is a long haul AV truck(e.g., commercial class 8 truck). Although alternatively referred to as“trucks,” autonomous vehicles can include any motor vehicles, such ascars, tractors (with or without trailers), buses, motorcycles,all-terrain vehicles, recreational vehicles, any specialized farming orconstruction vehicles, and the like), or any other self-propelledvehicles capable of being operated in a self-driving mode (without ahuman input or with a reduced human input). Autonomous vehicles caninclude vehicles with various levels of autonomy, such as level 2(partial autonomy) through level 5 (full autonomy). Autonomous vehiclescan include vehicles using an internal combustion engine (e.g., gasengine, diesel engine, etc.), an electric engine (motor), or combinationthereof (e.g., hybrid AV). AV 101 can be capable of traveling on pavedand/or unpaved roadways, off-road, on various surfaces encountered onfarming (or other agricultural) land, within a driving environment(including indoor environment) of an industrial plant, and so on.

AV 101 can include a sensing system 120. The sensing system 120 caninclude various electromagnetic (e.g., optical) and non-electromagnetic(e.g., acoustic) sensing subsystems and/or devices that can be used inobject sensing to facilitate autonomous driving, e.g., distance sensing,velocity sensing, acceleration sensing, rotational motion sensing, andso on. For example, optical sensing can utilize a range of light visibleto a human eye (e.g., the 380 to 400 nanometer (nm) wavelength range),the UV range (below 380 nm), the infrared range (above 400 nm), theradio frequency range (above 1 m), etc. In implementations, “optical”can include any other suitable range of the electromagnetic spectrum.

The sensing system 120 can include one or more LiDAR sensors 122 (e.g.,a LiDAR rangefinders), which can be laser-based units capable ofdetermining distances (e.g., using time-of-flight (ToF) technology) tothe objects in the environment around AV 101. For example, LiDARsensor(s) 122 can emit one or more laser signals (pulses) that travel toan object and then detect arrived signals reflected from the object. Bydetermining a time delay between the signal emission and the arrival ofthe retro-reflected waves, a ToF LiDAR sensors 122 can determine thedistance to the object. LiDAR sensor(s) 122 can emit signals in variousdirections to obtain a wide view of the outside environment. LiDARsensor(s) 122 can utilize wavelengths of electromagnetic waves that areshorter than the wavelength of the radio waves and can, therefore,provide a higher spatial resolution and sensitivity compared with theradar unit 124. In some implementations, LiDAR sensor(s) 122 can be (orinclude) coherent LiDAR sensor(s), such as a frequency-modulatedcontinuous-wave (FMCW) LiDAR sensor(s). FMCW LiDAR sensor(s) (or someother coherent LiDAR sensors) can use optical heterodyne detection forinstant velocity determination. LiDAR sensor(s) 122 can include one ormore laser sources producing and emitting signals and one or moredetectors of the signals reflected back from the objects, one or morespectral filters to filter out spurious electromagnetic waves havingwavelengths (frequencies) that are different from the wavelengths(frequencies) of the emitted signals, one or more directional filters(e.g., apertures, diffraction gratings, and so on) to filter outelectromagnetic waves that arrive at the detectors along directionsdifferent from the directions of the emitted signals, and othercomponents that can enhance sensing capabilities of the LiDAR sensor(s)122. In some implementations, LiDAR sensor(s) 122 can ensure a360-degree view in a horizontal direction and up to 90 degrees in thevertical direction.

The sensing system 120 can include one or more radar units 124, whichcan be any system that utilizes radio or microwave frequency signals tosense objects within the driving environment of the AV 101. The radarunit(s) 124 can be configured to sense both the spatial locations of theobjects (including their spatial dimensions) and their velocities (e.g.,using the Doppler shift technology), such as translational velocitiesand angular (rotational) velocities. Sensing system 120 can also includeone or more sonars 126, which can be ultrasonic sonars, in someimplementations.

Sensing system 120 can further include one or more cameras 128 tocapture images of the driving environment. The images can betwo-dimensional projections of the driving environment (or parts of thedriving environment) onto a projecting plane (flat or non-flat, e.g.fisheye) of the cameras. Some of cameras 128 of sensing system 120 canbe video cameras configured to capture a continuous (orquasi-continuous) stream of images of the driving environment.

The sensing data obtained by sensing system 120 can be processed by aperception system 130 that can be configured to detect and track objectsin the driving environment and to identify the detected objects. Forexample, perception system 130 can analyze images captured by cameras128 and can be capable of detecting traffic light signals, road signs,roadway layouts (e.g., boundaries of traffic lanes, topologies ofintersections, designations of parking places, and so on), presence ofobstacles, and the like. Perception system 130 can further receive theLiDAR sensing data (coherent Doppler data and incoherent ToF data) todetermine distances to various objects in the environment and velocitiesof such objects. In some implementations, perception system 130 can usethe LiDAR data in combination with the data captured by the camera(s)128. In one example, the camera(s) 128 can detect an image of a rockpartially obstructing a traffic lane. Using the data from the camera(s)128, the perception system 130 can be capable of determining the angularsize of the rock, but not the linear size of the rock. Using the LiDARdata, perception system 130 can determine the distance from the rock tothe AV and, therefore, by combining the distance information with theangular size of the rock, perception system 130 can determine the lineardimensions of the rock as well.

In another implementation, using the LiDAR data, perception system 130can determine how far a detected object is from the AV and can furtherdetermine the component of the object's velocity along the direction ofthe AV's motion. Furthermore, using a series of quick images obtained bythe camera, perception system 130 can also determine the lateralvelocity of the detected object in a direction perpendicular to thedirection of the AV's motion. In some implementations, the lateralvelocity can be determined from the LiDAR data alone, for example, byrecognizing an edge of the object (using horizontal scanning) andfurther determining how quickly the edge of the object is moving in thelateral direction.

Perception system 130 can further receive information from a GPStransceiver (not shown) configured to obtain information about theposition of the AV relative to Earth and use the GPS data in conjunctionwith the sensing data to help accurately determine location of the AVwith respect to fixed objects of the driving environment, such asroadways, lane boundaries, intersections, sidewalks, crosswalks, roadsigns, surrounding buildings, and so on, locations of which can beprovided by map information accessible by perception system 130. In someimplementations, perception system 130 can receive non-electromagneticdata, such as sonar data (e.g., ultrasonic sensor data), temperaturesensor data, pressure sensor data, meteorological data (e.g., wind speedand direction, precipitation data), or other environmental monitoringdata.

In some implementations, the perception system 130 can provide,generate, or be used to help generate sensor data 194 (e.g.,environmental sensing data, scenario sensing data, GPS data, etc.)pertaining to a route of a vehicle. Herein “route” refers to a sequenceof physical locations (e.g., geographic markers) that can be traveled bya target vehicle between a starting point (“start”) and a destinationpoint (“destination”). The start and/or the destination need not be theinitial and final locations of the vehicle in the driving mission, butcan be any two points (e.g., A and B) along such a mission. Accordingly,“mission” herein refers to any portion of the overall driving task.

Route data 182 can include information about the starting point,intermediate points and destination point of the route (e.g., longitudeand latitude information of points along the route) and include physicalcharacteristics of various routes. “Trajectory” refers to drivingsettings, specified for various locations along the route, and includesspeed, throttle, brake, etc. control that determine progression of thevehicle along the route. For example, a trajectory can include throttlesettings, T(L) as a function of the location L along the route, targetspeed of the vehicle S(L), gear selection sequences, and so on. Thelocation L can be identified by the distance travelled, GPS coordinates,road markers (e.g., mileposts), or a combination thereof, or in anyother way.

Topographic data 184 can include information about the topography of theroads (e.g., grade and radius of curvature, pitch, elevation, etc.) ortopography along the route.

Map data 186 can include information about the road network along theroute, such as the quality of road surfaces, number of lanes, regulatoryspeed limits (e.g., regulatory maximum speed limits, regulatory minimumspeed limits), type and number of exit ramps, availability of gasstations, and so on. Map data 186 can also include traffic data thatincludes information about historic traffic patterns or current trafficconditions along or near the route.

Vehicle data 188 can include data about the AV 101. Vehicle data 188 canbe physical vehicle data, such as total mass of the AV 101, brakingcapabilities of the AV (e.g., regenerative braking, friction braking,engine braking, downshifting, exhaust braking, using drive lineretarders, etc.), transmission gear ratios of the AV, wheelbase data ofthe AV, engine capabilities of the AV, lateral dynamics data (e.g., howthe AV reacts to winding roads), etc.

Historical data 192 can include data, such as recommended lane data(e.g., to merge, historically it is better to be in a certain lane),historical wind data (e.g., particular road segments historically have aparticular speed and direction of wind), traffic data (e.g.,historically a certain amount of traffic at particular road segments atparticular times or days, historically vehicles are at a particularspeed on particular road segments at particular times or days, etc.). Insome implementations, the historical data 192 is collected from AVs 101over time (e.g., via sensing system 120, via perception system 130, sentto AV server 150, etc.). The historical data 192 can be used aspredictive data about future scenarios. For example, sensor data 194 canindicate that another vehicle is in an adjacent lane and has an engagedturn signal, the historical data 192 can include information indicatingthat historically, the vehicle will enter the same lane that AV 101currently occupies in 3 seconds and will be approximately 3 meters infront of the AV 101 at that time.

In some implementations, the wind data is sensor data (e.g., from flowrate sensors, pressure sensors) from one or more AVs 101. In someimplementations, the wind data is from a weather report. In someimplementations, the fuel-economy optimization module 142 calculates thewind data based on speed values, steering input values, and throttleinput values one or more AVs 101 over time compared to steady statevalues of AVs 101.

Sensor data 194 (e.g., environmental sensing data) can include dataobtained by sensing system 120 and/or include data from the perceptionsystem 130 that has been generated using the data from the sensingsystem 120. For example, sensor data 194 (e.g., environmental sensingdata) can include information describing the environment of or proximatethe AV 101 (e.g., position of other vehicles, obstacles, or otherelements with respect to the AV 101).

Fuel economy data 196 can include input values and output values. Theoutput values may be collected by AVs driving based on the input values.The input values can include one or more of speed values (e.g., mph),total AV mass values, wind values, grade values, road curvature values,etc. The output values can include fuel economy values (e.g., mpg). Forexample, the fuel economy data 196 may indicate that at a particularspeed, particular total AV mass, wind, grade, and road curvature, AVshad a particular average fuel economy (e.g., mpg).

In some implementations, the fuel economy data 196 further indicatestransmission gear (e.g., input or output value), braking system (e.g.,input or output value), etc. For example, the fuel economy data 196 mayindicate that at a particular speed and transmission gear, AVs had aparticular average fuel economy. In another example, the fuel economydata 196 may indicate that for a particular downhill grade, a particulartotal AV mass, and a particular radius of curvature, AVs had aparticular average fuel economy and used a particular braking system.

In some implementations, a first portion of the input and output valuesin the fuel economy data 196 is collected (e.g., based on sensor data194, vehicle data 188, topographic data 184, etc.) and a second portionof the input and output values in the fuel economy data 196 is estimated(e.g., extrapolated, etc.) based on the first portion of input andoutput values. For example, if fuel economy values collected at 30 mphand at 35 mph are the same for an AV, the fuel economy data 196 mayindicate that from 30 mph to 35 mph, the fuel economy values are thesame.

The fuel economy data 196 can be included in a file (e.g., text file), atable (e.g., a lookup table), or any other data structure.

Speed profile 198 can include a speed value for each segment of a route.In some implementations, the speed profile 198 includes additionalinformation (e.g., transmission gear to use, braking system to use,acceleration value, deceleration value, etc.) for one or more segmentsof the route (e.g., instead of or in addition to the speed value foreach segment of the route). In some implementations, the speed profile198 is a file (e.g., text file). In some implementations, the speedprofile 198 is embedded in other data (e.g., map data 186, route data182, etc.).

The data generated by perception system 130 as well as variousadditional data (e.g., GPS data, route data 182, topographic data 184,map data 186, vehicle data 188, historical data 192, sensor data 194,fuel economy data 196, speed profile 198, and the like) can be used byan autonomous driving system, such as AV 101 control system (AVCS 140).The AVCS 140 can include one or more algorithms that control how AV 101is to behave in various driving situations and environments. Forexample, the AVCS 140 can include a navigation system for determining aglobal driving route to a destination point. The AVCS 140 can alsoinclude a driving path selection system for selecting a particular paththrough the immediate driving environment, which can include selecting atraffic lane, negotiating a traffic congestion, choosing a place to makea U-turn, selecting a trajectory for a parking maneuver, and so on. TheAVCS 140 can also include an obstacle avoidance system for safeavoidance of various obstructions (rocks, stalled vehicles, a jaywalkingpedestrian, and so on) within the driving environment of the AV. Theobstacle avoidance system can be configured to evaluate the size of theobstacles and the trajectories of the obstacles (if obstacles areanimated) and select an optimal driving strategy (e.g., braking,steering, accelerating, etc.) for avoiding the obstacles.

Algorithms and modules of AVCS 140 can generate instructions for varioussystems and components of the vehicle, such as vehicle systems 160(e.g., the powertrain, steering and braking 162, vehicle electronics164, and signaling 166), and other systems and components not explicitlyshown in FIG. 1 . The powertrain, steering and braking 162 can includean engine (internal combustion engine, electric engine (motor), and soon), transmission (e.g., transmission gears), differentials, axles,wheels, steering mechanism, braking mechanism, and other systems. Thevehicle electronics 164 can include an on-board computer, enginemanagement, ignition, communication systems, carputers, telematics,in-car entertainment systems, and other systems and components. Thesignaling 166 can include high and low headlights, stopping lights,turning and backing lights, horns and alarms, inside lighting system,dashboard notification system, passenger notification system, radio andwireless network transmission systems, and so on. Some of theinstructions output by the AVCS 140 can be delivered directly to thepowertrain, steering and braking 162 (or signaling 166), whereas otherinstructions output by the AVCS 140 are first delivered to theelectronics 164, which can generate commands to the powertrain, steeringand braking 162 and/or signaling 166.

In one example, the AVCS 140 can determine that an obstacle identifiedby perception system 130 is to be avoided by decelerating the vehicleuntil a safe speed is reached, followed by steering the vehicle aroundthe obstacle. The AVCS 140 can output instructions to the powertrain,steering and braking 162 (directly or via the electronics 164) to 1)reduce, by modifying the throttle settings, a flow of fuel to the engineto decrease the engine rpm, 2) downshift, via an automatic transmission,the drivetrain into a lower gear, 3) engage a brake unit to reduce(while acting in concert with the engine and the transmission) thevehicle's speed until a safe speed is reached, and 4) perform, using apower steering mechanism, a steering maneuver until the obstacle issafely bypassed. Subsequently, the AVCS 140 can output instructions tothe powertrain, steering and braking 162 (directly or via theelectronics 164) to resume the previous speed settings of the vehicle.

In some implementations, architecture 100 can also include AV server 150to communicate relevant information to and receive relevant informationfrom AV 101. For example, relevant information can include trafficinformation, weather information, route information, among otherinformation. In some implementations, AV server 150 can be, at least attimes, communicating with AV 101 via network 170. In someimplementations, AV 101 can be connected to network 170 at most or alltimes. In some implementations, AV 101 can establish connections tonetwork 170 intermittently, when an appropriate network signal isavailable. In some implementations, AV 101 can be connected to network170 prior to starting the driving mission. Network 170 can use awireless connection, such as a broadband cellular connection (e.g., 3G,4G, 4G LTE, 5G, connection(s), and so on), a wireless local area network(WLAN), a wireless wide area network (WWAN), a wired connection, asatellite connection, or the like. Connection to network 170 can befacilitated via a network interface 106 (on the side of AV 101) and anetwork interface 152 (on the side of AV server 150). Network interfaces106 and 152 can include antennas, network controllers, radio circuits,amplifiers, analog-to-digital and digital-to-analog converters, physicallayers (PHY), media access control layers (MAC), and the like.

In some implementations, architecture 100 can also include a datarepository 180. In some implementations, the data repository 180 ismemory (e.g., random access memory), a drive (e.g., a hard drive, aflash drive), a database system, or another type of component or devicecapable of storing data. In some implementations, data repository 180includes multiple storage components (e.g., multiple drives or multipledatabases) that span multiple computing devices (e.g., multiple servercomputers). In some implementations, the data repository 180 stores oneor more of route data 182, topographic data 184, map data 186, vehicledata 188, historical data 192, sensor data 194, fuel economy data 196,speed profile 198, and the like. In some implementations, at least aportion of the data shown in FIG. 1 as being stored in data repository180 is stored in AV server 150 and/or AV 101.

In some implementations, architecture 100 includes a fuel-economyoptimization module 142. In some implementations, the fuel-economyoptimization module 142 is hosted by the AV server 150. In someimplementations, the fuel-economy optimization module 142 is hosted bythe AV 101 (e.g., in AVCS 140). In some implementations, the AVCS 140includes one or more of fuel-economy optimization module 142, routingmodule 144, and/or motion control module 146.

In some implementations, the routing module 144 identifies data, such asroute data 182, map data 186, and sensor data 194, and generates, basedon the data, instructions (e.g., short time horizon routing data). Forexample, routing module 144 receives route data 182 indicating that theAV 101 is to travel along a particular road, map data 186 indicatingregulatory speed limits of the particular road, and sensor data 194indicating locations of vehicles and/or objects proximate the AV 101.The routing module 144 generates, based on the route data 182, map data186, and sensor data 194, instructions (e.g., commands, short timehorizon routing data) of vehicle actions of the AV 101 for the nextinterval (e.g., 10 seconds). The routing module 144 transmits theinstructions to the motion control module 146 and the motion controlmodule 146 controls one or more of the actuators (e.g., the vehiclesystems 160) of the AV 101 based on the instructions for the nextinterval (e.g., 10 seconds). The routing module 144 continues generatinginstructions for the next interval (e.g., based on current route data182, map data 186, and sensor data 194), transmitting the instructionsto the motion control module 146, and the motion control module controlsthe actuators based on the instructions.

In some implementations, the fuel-economy optimization module 142 caninterface with routing module 144 and motion control module 146. Theoperations of fuel-economy optimization module 142 are further describedbelow in conjunction with the following Figures.

The fuel-economy optimization module 142 identifies (e.g., retrievesfrom data repository 180 or receives from appropriate AV components orAV server) data, such as route data 182, topographic data 184, map data186, vehicle data 188, historical data 192, sensor data 194, etc. Theroute data 182 may include a threshold arrival time.

The fuel-economy optimization module 142 retrieves fuel economy data 196that is based on the vehicle data 188 of the AV 101 (e.g., fuel economydata 196 corresponding to the total AV mass of the AV 101, etc.). Thefuel-economy optimization module 142 determines, based on the fueleconomy data 196, a fuel efficient speed value for each segment of theroute. In some implementations, the fuel economy data 196 is stored in atable (e.g., look-up table). The fuel-economy optimization module 142determines the correlation of different speed values (e.g., mph) todifferent fuel economy values (e.g., mpg) for each segment of the route(e.g., based on the total AV mass, grade, wind, radius of curvature,etc.) and chooses the speed values (e.g., referred to as fuel efficientspeed values) that have the best fuel economy values for each segment.

The fuel-economy optimization module 142 calculates, based on the routedata 182 (e.g., distance value of each segment of the route) and thefuel-efficient speed value of each segment, an estimated arrival time(e.g., the sum of each distance value divided by a correspondingfuel-efficient speed value for the segments of the route).

Responsive to the estimated arrival time meeting the threshold arrivaltime (e.g., the AV 101 would arrive by the latest arrival time), thefuel-economy optimization module 142 generates a speed profile 198 thatincludes a fuel-efficient speed value for each segment of the routedetermined based on the fuel economy data 196.

Responsive to the estimated arrival time not meeting the thresholdarrival time (e.g., the AV 101 would arrive after the latest arrivaltime), the fuel-economy optimization module 142 determines whether thereare any segments that are a candidate for speed increase (e.g.,determines whether any segment has a fuel-efficient speed value that hasnot met a regulatory maximum speed or a historical maximum speed basedon historical traffic data).

Responsive to no segments being a candidate for speed increase, thefuel-economy optimization module 142 generates a speed profile 198 basedon the fuel efficient speed values for each segment.

Responsive to the fuel-economy optimization module 142 identifying atleast a subset of the segments that each represent a candidate for speedincrease, the fuel-economy optimization module 142 computes, for eachsegment in the subset and based on the fuel economy data, acorresponding correlation metric that indicates a correlation between achange in fuel economy and a change in speed for a segment in thesubset. For example, the correlation metric may indicate a decrease inmpg for different amounts of increase in mph. The fuel-economyoptimization module 142 increases, for at least one segment from thesubset and based on a respective correlation metric, a fuel-efficientspeed value of a corresponding segment from the subset to provide thespeed profile 198 reflecting the increased fuel-efficient speed valuefor the corresponding segment.

The AV 101 is controlled to travel along the route based on the speedprofile 198. In some implementations, the AV 101 travelling the routebased on the speed profile has an estimated arrival time that meets thethreshold arrival time (e.g., AV 101 estimated to arrive at thedestination by the latest arrival time, AV 101 is not to exceed themaximum trip time, etc.).

The fuel-economy optimization module 142 provides the speed profile 198to the AVCS 140 (e.g., routing module 144 and/or motion control module146) to control the vehicle systems 160 based on the speed profile 198.In some implementations, speed profile 198 is embedded in the map data186 that is provided to the AVCS 140 (e.g., routing module 144).

In some implementations, the speed profile 198 includes additional data(e.g., gear ratio to be used, gear to be used, type of control ofpowertrain, type of braking, acceleration value, deceleration value,etc.) for one or more of the segments instead of or in addition to thefuel-efficient speed value for the segments of the route.

The use of the speed profile 198 provides fuel-economy optimization,such as decreasing wear-and-tear on the vehicle systems 160 of the AV101, providing energy savings (e.g., an energy savings action), and/orthe like. An energy saving action can refer to a vehicle action thatresults in reduction of energy consumed by an AV. With respect to an AVwith an internal combustion engine (ICE), an energy saving action caninclude a fuel saving action. With respect to an AV with an electricengine (e.g., electric motor) or hybrid AV, an energy saving action caninclude a power or electricity saving action. In some implementations,an energy saving action can include at least one of a disengagement of apowertrain of the AV, a withholding of a supply of energy to an engineof the AV, or a regenerative energy action. Disengagement of apowertrain can include placing the AV in neutral gear (e.g. coasting) ordecoupling the power of the engine from the wheels. Withholding a supplyof energy to an engine of the AV 101 can include reducing or stoppingfuel injection to the ICE or reducing or stopping the electricityprovided to the electric engine (e.g., motor). A regenerative energyaction can include an action that returns to or generates energy for theAV. A regenerative braking technique that returns energy to the AVthrough braking or other regenerative technique can be implemented. Asused herein, fuel-economy optimization, fuel-efficient speed value,fuel-economy data, and the like may refer to any type of energy savings(e.g., savings of one or more of electricity, gasoline, diesel,biodiesel, natural gas, petroleum gas, methanol, ethanol, propane,hydrogen, regenerative energy, solar energy, etc.).

FIG. 2 is a diagram illustrating components of an example architecture200 of a system and example data flows pertaining to fuel-economyoptimization, in accordance with some implementations of the disclosure.Components of FIG. 1 are used to help describe aspects of FIG. 2 .

In some implementations, the fuel-economy optimization module 142provides fuel-economy optimization for the AV. In some implementations,an AV server 150 includes the fuel-economy optimization module 142. Insome implementations, the AVCS 140 of the AV includes the fuel-economyoptimization module 142.

The fuel-economy optimization module 142 receives contextual data 210,such as one or more of route data 182, topographic data 184, map data186, vehicle data 188, historical data 192, sensor data 194, and/or thelike. The fuel-economy optimization module 142 retrieves a fuel economydata 196 based on at least a portion of the contextual data 210 (e.g.,vehicle data 188). The fuel-economy optimization module 142 generates aspeed profile 198 based on the contextual data 210 and fuel economy data196. In some implementations, the speed profile 198 is a text file, ascript, an executable binary file, and/or the like. In someimplementations, the fuel-economy optimization module 142 embeds thespeed profile 198 in other data, such as the map data 186. Thefuel-economy optimization module 142 provides the speed profile 198(e.g., alone, embedded in other data, etc.) to the routing module 144.In some implementations, the fuel-economy optimization module 142provides the speed profile 198 to the routing module 144 and the motioncontrol module 146.

In some implementations, routing module 144 is the primary authorityand/or component involved in routing and decision making on positioningand operation of the AV. The routing module 144 receives data, such asthe speed profile 198, route data 182, map data 186, and sensor data194, and makes decision about the positioning of the AV with respect tothe external environment based on the data received.

The routing module 144 generates instructions 220 (e.g., associated withmoving the AV over the next 10 seconds) based on at least a portion ofthe speed profile 198 and transmits the instructions 220 to the motioncontrol module 146. In some implementations, the instructions 220 are ina file (e.g., a text file, etc.) and the motion control module 146generates commands (e.g., script) to control the vehicle systems 160based on the instructions 220. In some implementations, the instructions220 include commands (e.g., a script) and the motion control module 146passes the commands (e.g., as received or after updating the commands)to the vehicle systems 160 to control the vehicles systems 160. Themotion control module 146 executes the instructions 220 (e.g., commands,such as a speed value) based on the speed profile 198 (e.g.,constraints, such as a speed value that may be different from themaximum speed limit or the minimum speed limit). In someimplementations, the AVCS 140 controls the position of the AV based on avery strict tolerance (e.g., within a few centimeters from the requestedposition). For example, the AVCS 140 can evaluate received data (e.g.,sensor data 194 indicating location of objects proximate the AV) anddetermine a position of the AV with respect to the external environmentto move the AV. In some examples, the routing module 144 receives thesensor data 194 indicating that another vehicle is two seconds ahead ofthe AV. The routing module 144 then generates instructions 220indicating that the braking system is to be actuated to cause the AV tobe at least three seconds behind the other vehicle. In someimplementations, the motion control module 146 is expected to executethe instructions 220 (e.g. in view of the speed profile 198) within theconstraints imposed by the instructions 220 (e.g. in view of the speedprofile 198) such that the position of the AV as determined by the AVCS140 can be controlled with precision.

In some examples, speed profile 198 can indicate, for a segment of aroute, a calculated maximum speed (e.g., that is less than a regulatorymaximum speed), a type of braking, a gear ratio to be used, a rate ofdeceleration, and/or a lane in which to travel. The fuel-economyoptimization module 142 can send at least a first portion of the speedprofile 198 (e.g., the speed value, rate of deceleration, lane in whichto travel, etc.) to the routing module 144 and at least a second portionof the speed profile 198 (e.g., type of braking, gear ratio, etc.) tothe motion control module 146. The routing module 144 can generateinstructions 220 for the next interval of time (e.g., 10 seconds) basedon the at least a first portion of the speed profile 198 (e.g.,calculated maximum speed, rate of deceleration, lane in which to travel,etc.). The motion control module 146 can control the vehicle systems 160based on the at least a second portion of the speed profile 198 (e.g.,type of braking and/or gear ratio of the speed profile 198) and based onthe instructions 220.

FIG. 3 depicts a flow diagram of an example method 300 of performingfuel-economy optimization, in accordance with some implementations ofthe disclosure. Method 300 and/or each of the individual functions,routines, subroutines, or operations of method 300 can be performed by aprocessing device, having one or more processing units (CPU) and memorydevices communicatively coupled to the CPU(s). The processing deviceexecuting methods 300 can be part of a server (located outside anautonomous vehicle, such as AV server 150) or a client processing module(located within or at the autonomous vehicle, such as AVCS 140), or anycombination thereof. In some implementations, method 300 can beperformed by a single processing thread or alternatively by two or moreprocessing threads, each thread executing one or more individualfunctions, routines, subroutines, or operations of the method. Themethod 300 as described below can be performed by processing logic thatcan include hardware (e.g., processing device, circuitry, dedicatedlogic, programmable logic, microcode, hardware of a device, integratedcircuit, etc.), software (e.g., instructions run or executed on aprocessing device), or a combination thereof. In some implementations,method 300 is performed by fuel-economy optimization module 142described in FIGS. 1 and 2 . Although shown in a particular sequence ororder, unless otherwise specified, the order of the operations can bemodified. Thus, the illustrated implementations should be understoodonly as examples, and the illustrated operations can be performed in adifferent order, while some operations can be performed in parallel.Additionally, one or more operations can be omitted in someimplementations. Thus, not all illustrated operations are required inevery implementation, and other process flows are possible. In someimplementations, the same, different, fewer, or greater operations canbe performed.

At operation 302, processing logic identifies route data including athreshold arrival time of a route for an AV. In some implementations,the threshold arrival time can include a departure time and a maximumtrip time. In some implementations, the threshold arrival time caninclude a latest arrival time (e.g., latest arrival time allowed, cargodelivery deadline, etc.). In some implementations, the threshold arrivaltime can include a preference to travel during a particular time of day(e.g., drive during daylight hours and avoid driving at night, avoiddriving during inclement weather conditions, etc.).

In some embodiments, the processing logic receives a starting locationand destination location (e.g., via user input) that are within a mappedgeography of the AV. The processing logic may determine a route (e.g.,an optimal route) based on the starting location and destinationlocation. The processing logic may further determine the route based onthe threshold arrival time. The processing logic may further determinethe route based on map data (e.g., from a map server). The processinglogic may further receive topographic data (e.g., road profileinformation, such as length values and grade values), map data (e.g.,regulatory speed limits, such as regulatory minimum speed limit andregulatory maximum speed limit), historical data (e.g., historicaltraffic data, historical wind data, etc.), and/or the like for differentportions of the route. In some implementations, the route data includesthe corresponding distance value, corresponding grade value,corresponding estimated wind value, etc. for each of the segments of theroute. In some implementations, the route data includes a trip roadprofile which may include an elevation graph of the entire trip from thestarting location to the destination location which allows for energycalculations as well as speed and time calculations.

At operation 304, processing logic divides the route into segments. Insome implementations, each of the segments has a minimum threshold speedvalue and a maximum threshold speed value that are substantiallyconstant over a length of the segment (e.g., a segment has constantregulatory speed limits, the segment has a constant historical maximumspeed value based on traffic data). In some implementations, each of thesegments has a corresponding grade that is substantially the same gradevalue over a length of the corresponding segment. In someimplementations, each segment has a corresponding radius of curvaturethat is substantially the same over a length of the correspondingsegment.

At operation 306, processing logic determines, based on fuel economydata, a corresponding fuel efficient speed value for each of thesegments of the route. In some implementations, the fuel economy data isbased on the vehicle data (e.g., total mass of the AV) and/or type ofpowertrain (e.g., different powertrains may have different fuelconsumption at different speeds). In some implementations, theprocessing logic stores the fuel-efficient speed values in a speedprofile (e.g., stored as a text file, a table, a script, etc.).

In some implementations, the fuel economy data includes input valuesincluding speed values, grade values, total mass values (e.g., combinedtractor plus cargo mass), wind values, and/or the like. The fuel economydata may include output values of fuel economy values (e.g., specificfuel consumption values, mpg) collected from one or more AVs whiledriving based on the input values. The fuel economy data may be a fueleconomy table. The input values and output values may be dimensions ofthe fuel economy table.

In some implementations, the fuel economy data is updated based onsensor data from the AV. For example, the processing logic may receivesensor data associated with the AV driving at a first speed value,determine a fuel economy value based on the sensor data, and cause thefuel economy data to be updated based on the first fuel economy value atthe first speed value. In some implementations, the same fuel economydata is used by similar AVs (e.g., AVs that have substantially the sametotal AV mass, that have substantially the same type of power train,etc.). In some implementations, fuel economy data is personalized for aspecific AV based on the sensor data of that AV. Responsive to fueleconomy data for a specific AV being updated with a first fuel economyvalue that is not within a threshold range of fuel economy valuesassociated with similar AVs, the processing logic may provide an alert.In some implementations, the alert indicates that the AV has a fueleconomy that is not within a threshold range of similar AVs (e.g.,maintenance is to be performed so that the AV can have a fuel economywithin the threshold range of fuel economies of similar AVs). The fueleconomy data may be updated (e.g., parameters of the fuel economy tablemay be updated) based on live measurements as the AV drives. This mayoptimize fuel economy for the specific AV. Issues with AVs over time maybe diagnosed by determining differences (e.g., looking for majordifferences, identifying differences in fuel economy data) with respectto other AVs in the fleet.

In some implementations, the processing logic collects fuel consumptionvalues from the AV while driving (e.g., the engine controller providesinstantaneous fuel consumption). In some implementations, one or moresimilar AVs are driven (e.g., on an open or closed course) and data iscollected across the range of the parameters of interest. The fueleconomy data may be a high dimensional lookup table of fuel economycompared to other factors (e.g., road speed, road profile such as pitch,cargo weight, wind, etc.) that is created based on the data collected(e.g., fuel consumption values, speed values, etc.). The fuel economydata may take into account factors that change from trip to trip. Insome implementations, the fuel economy data may not include factors thatchange over longer periods of time (e.g., to make it easier and fasterto build the fuel economy data).

The fuel economy data can be used to optimize the fuel economy of an AVfor any trip (e.g., route). Various inputs are sourced for thecalibration of the fuel economy data, such as wind conditions along theroute (e.g., via weather stations, via AVs, etc.), traffic conditions(e.g., via estimations, via historical data, etc.), total mass (e.g.,cargo weighting which may be available on the e-bill of landing), roadprofile and condition (e.g., stored in a database as part of the basemap), and/or the like.

The fuel economy data may indicate the most fuel efficient speed for anAV based on other conditions (e.g., grade value, wind value, etc.).

In some implementations, the processing logic determines a regulatorymaximum speed value and a regulatory minimum speed value for eachsegment of the route (e.g., based on map data). The processing logic mayfurther determine a historical maximum speed value for segments of theroute based on historical traffic data. For example, the historicaltraffic data may indicate a historical maximum speed value forparticular segments (e.g., at particular times, such as rush hour) thatis less than a regulatory maximum speed value. The processing logic mayupdate the fuel-efficient speed values based on minimum threshold speedvalues (e.g., regulatory minimum speed values) and maximum thresholdspeed values (e.g., regulatory maximum speed values, historical maximumspeed values). For example, if the processing logic determines afuel-efficient speed value of 30 mph based on the fuel economy data anda minimum threshold speed value of 35 mph, the processing logic mayupdate the fuel-efficient speed value to be 35 mph. In someimplementations, the processing logic updates (e.g., replaces) thefuel-efficient speed values included in a speed profile.

In some implementations, the regulatory minimum speed value (e.g.,minimum legal limits on vehicle speed) is a minimum speed that the AV isallowed to travel on a particular section of road. In someimplementations, the regulatory minimum speed is a constraint thatcannot normally be broken, except during circumstances such as adverseweather conditions or heavy traffic. In some implementations, theregulatory maximum speed value (e.g., maximum legal limits on vehiclespeed) is a maximum speed that a truck is allowed to travel on aparticular section of road (e.g., a hard constraint that cannot bebroken).

In some implementations, the processing logic further determines themaximum threshold speed values and the minimum threshold speed valuesbased on environmental and vehicle factors, such as one or more of wind,tire wear, tire pressure, road surface condition, engine andtransmission type and condition, and/or the like.

At operation 308, processing logic calculates, based on the route dataand the corresponding fuel-efficient speed value for each of thesegments, an estimated arrival time.

To calculate the estimated arrival time, the processing logic mayperform route segment integration based on a corresponding length ofeach of the segments and a fuel-efficient speed value for each of thesegments. In some implementations, in order to perform route segmentintegration, the processing logic determines a segment travel time foreach segment of the route by dividing the distance value of each segmentby the fuel-efficient speed value for each segment and then addstogether each segment travel time to determine a total travel time totravel the route. The estimated arrival time may also include a buffer(e.g., a 10% buffer). The estimated arrival time may be the departuretime plus the total amount of time to travel the route plus a buffer.

At operation 310, processing logic determines whether the estimatedarrival time meets the threshold arrival time. Responsive to theestimated arrival time meeting the threshold arrival time (e.g., the AVis estimated to arrive at or before the arrival time deadline), the flowcontinues to operation 320. Responsive to the estimated arrival time notmeeting the threshold arrival time (e.g., the AV is estimated to arriveafter the arrival time deadline), the flow continues to operation 312.

At operation 314, processing logic determines whether the correspondingfuel-efficient speed value for each of the segments meets acorresponding maximum threshold speed value for the correspondingsegment. For example, the processing logic may determine whether all ofthe fuel-efficient speed values for the segments are the same as eithera corresponding regulatory maximum speed value for the correspondingsegment or a corresponding historical maximum speed value for thecorresponding segment (e.g., the vehicle speed are clamped to themaximum limits across all route segments). Responsive to thecorresponding maximum threshold speed values being met, flow continuesto operation 320. Responsive to the maximum threshold speed values forall of the segments not being met (e.g., the fuel-efficient speed valuefor at least one of the segments does not meet a corresponding maximumthreshold speed value), flow continues to operation 314.

At operation 314, processing logic identifies at least a subset ofsegments that each represent a candidate for speed increase. In someimplementations, the subset of segments that each represent a candidatefor speed increase are each of the segments that have a fuel-efficientspeed value that is less than a corresponding maximum threshold speedvalue. In some implementations, the subset of segments are furtherlimited (e.g., segments that have at least a threshold distance, atleast a threshold difference between fuel-efficient speed value andmaximum threshold speed value, etc.).

At operation 316, processing logic computes, for each segment in thesubset and based on the fuel economy data, a correlation metric thatindicates a correlation between a change in fuel economy and a change inspeed. In some implementations, the different fuel economies areinterpolated between points. The correlation metric is based on thedecrease of fuel economy for an increase in speed. For example, a speedvalue increase of 5 mph for a first segment of the route may decreasefuel economy (e.g., miles per gallon (mpg)) for the first segment by afirst value and a speed value increase of 5 mph for a second segment maydecrease fuel economy for the second segment by a second value. In someimplementations, the correlation metric is based on differences betweendata points. In some implementations, an equation is fit to the datapoints (e.g., fuel economy values and speed values) and the correlationmetric is a derivative of the equation. In some implementations, thecorrelation metric is a mathematical derivative of the data points(e.g., fuel economy values and speed values), such as a difference inmpg compared to difference in mph.

At operation 318, processing logic increases, for at least one segmentfrom the subset and based on a respective correlation metric, afuel-efficient speed value of a corresponding segment from the subset.One or more fuel-efficient speed values may be increased based on thecorrelation metrics. Increasing one or more fuel-efficient speed valuesin operation 318 allows the AV to drive faster (e.g., meet the thresholdarrival time) in the most efficient manner. In some implementations, theprocessing logic includes the increased fuel-efficient speed values in aspeed profile.

After operation 318, flow returns to operation 310 for recomputing theestimated arrival time based on the route data and the newfuel-efficient speed values (e.g., included in the speed profile). Insome implementations, the processing logic adjusts the correspondingfuel-efficient speed values until local minima are found that minimizethe amount of fuel that is to burn (e.g., to meet the threshold arrivaltime) based on factors the user cannot control.

At operation 320, processing logic generates (e.g., provides) a speedprofile (e.g., a text file, a script, etc.) reflecting thefuel-efficient speed value for each of the segments. In someimplementations, the speed profile is generated based on more than oneoptimization parameter (e.g., more than just topologic data). In someimplementations, the speed profile includes one or more fuel-efficientspeed values from the fuel economy data. In some implementations, thespeed profile includes one or more fuel-efficient speed values that havebeen increased to meet a minimum threshold speed value (e.g., regulatoryminimum speed value) compared to the fuel economy data. In someimplementations, the speed profile includes one or more fuel-efficientspeed values that have been decreased to meet a maximum threshold speedvalue (e.g., regulatory maximum speed value, historical maximum speedvalue) compared to the fuel economy data. In some implementations, thespeed profile includes one or more fuel-efficient speed values that havebeen increased to meet the threshold arrival time. In someimplementations, the speed profile includes additional information(e.g., transmission gear to be used, type of braking, etc.) in additionto or instead of speed values for one or more segments of the route.

In some implementations, at operation 322, processing logic adjustschange in speed between segments in the speed profile to meet athreshold speed difference value. For example, the processing logic maydetermine, based on the speed profile, that a difference between a firstfuel-efficient speed value of a first segment of the route and a secondfuel-efficient speed value of a subsequent segment of the route exceedsa threshold speed difference value. The processing logic may adjustchange in speed (e.g., gradually accelerate or decelerate, apply asmoothing function to avoid sudden speed changes) between the firstsegment and the subsequent segment in the speed profile to meet thethreshold speed difference value. In some implementations, the speedprofile is the set of speeds that provides the lowest integral fuel burnover the entire route. The AV is to travel along the route based on thespeed profile.

In some implementations, the processing logic repeats one or more ofoperations 302-322 to update the speed profile (e.g., continuouslyanalyze the lower bound of vehicle speed that would still have thevehicle arrive on time). In some implementations, as the AV drives alongthe route, one or more parameters from method 300 (e.g., the initialroute optimization calculation) change, such as changes in estimates ofwind and traffic, updates to the fuel economy data, changes to the route(e.g., given new road blockage information), etc. As these changes areregistered, the processing logic (e.g., at the AV server, at the AV,etc.) may re-run method 300 (e.g., the same optimization process) and/orthe generation of the fuel economy data to generate an updated speedprofile so that the AV continues driving the route in the most optimalmanner. In some implementations, the frequency of this computation(e.g., re-running method 300, updating the fuel economy data, etc.) maybe adjusted and may be triggered by certain events, such as largechanges to one or more of the input parameters (e.g., wind and trafficestimates, route changes, fuel economy data updates, etc.) to avoidcomputation when the speed profile would not change significantly. Theroute data may include dynamic variables, such as wind data, weatherdata, traffic data, road closure data, etc. The dynamic variables of theroute data may be updated (e.g., continuously updated) and one or moreof blocks 302-322 of method 300 may be repeated with the updated routedata (e.g., updated wind data, updated weather data, updated trafficdata, updated road closure data, etc.).

In some implementations, over time the conditions of the AV change(e.g., engine and/or transmission efficiency, tire wear, etc.) which mayhave effects on the fuel efficiency at different operating conditions.As the changes occur, the processing logic may update the fuel economydata of the AV with new values that are continuously collected bymonitoring specific fuel consumption and updating the appropriateportions of the fuel economy data related to the current operatingcondition of the AV. Updates to the fuel economy data allow each AV inan AV fleet to optimize itself, such that the fleet as a whole is fullyoptimized.

In some implementations, a reasonable band of fuel economy data valuesis determined (e.g., by a fleet management server) over time for a fleetof AVs (e.g., AV tractors). The fleet management server can use thisinformation to compare against specific AVs within the fleet and confirmwhether each AV is operating within the reasonable band (e.g., somedetermined band of the norm). If an AV does not meet a threshold value(e.g., is particularly far away from the average values), the AV can beautomatically tagged for inspection to figure out what is wrong with theparticular vehicle. By tightening the band, fuel efficiency issues inthe fleet of AVs can be identified early on before the issues result inlarge costs. In some implementations, after collecting data, the AVsthat have achieved the best fuel economy of the fleet of AVs can beinspected to identify factors which contributed to the high fueleconomy. If these factors are within control (e.g., aerodynamicfairings, tire pressure, tire wear), these factors can be adjustedacross the fleet of AVs.

In some embodiments, the processing logic determines, based on sensordata (e.g., from perception system) that there are no upcoming uphillgrades for a particular segment (e.g., multiple miles) and there are novehicles behind the AV during that segment. The processing logic thenupdates the speed profile to slow the AV to go into a low performancestate (e.g., slower speed since the AV should not be requested to have asudden increase in torque).

In some implementations, instead of the processing logic firstdetermining a fuel-efficient speed value for each of the segments of theroute (e.g., block 306 of method 300) and then revising thefuel-efficient speed values (e.g., block 318 of method 300), theprocessing logic determines an estimated arrival time (e.g., prior tooptimizing speed values based on fuel economy data) and then optimizesspeed values based on fuel economy data. The estimated arrival time maybe based on speed values (e.g., a preliminary speed profile) for thesegments of the route. In some implementations, each of the speed values(e.g., average speed values, regulatory speed values, maximum and/orminimum speed values, etc.) for segments of the route could be decreasedor increased proportionally to meet a threshold arrival time (e.g., eachspeed value is decreased by 5% to arrive at the threshold arrival time,each speed value is increased by 3% to arrive by the threshold arrivaltime, etc.).

After having speed values for segments of the route that meet thethreshold arrival time, the processing logic may optimize the speedvalues (e.g., for fuel economy). For example, the processing logic maydetermine a first subset of segments that each represent a candidate forspeed increase (e.g., similar to block 314 of method 300) and theprocessing logic may determine a second subset of segments that eachrepresent a candidate for speed decrease (e.g., are not less than aminimum threshold speed value). The processing logic may compute, foreach segment in the first subset and the second subset and based on thefuel economy data, a correlation metric that indicates a correlationbetween a change in fuel economy and a change in speed (e.g., similar toblock 316 of method 300). The processing logic may increase, for atleast one segment from the first subset and based on a respectivecorrelation metric, a fuel-efficient speed value of the correspondingsegment from the first subset (e.g., similar to block 318 of method 300)and the processing logic may decrease, for one or more segments from thesecond subset and based on a corresponding correlation metric, afuel-speed value of the respective segment from the second subset. Theprocessing logic may adjust (e.g., increase or decrease) differentfuel-speed values while still meeting the threshold arrival time (e.g.,the original estimated arrival time). For example, the processing logicmay decrease the speed value of a first segment (e.g., where the AV haslower fuel economy) and may increase the speed value of a second segment(e.g., where the AV has a higher fuel economy) to still meet a thresholdarrival time. The processing logic adjusts (e.g., increases, decreases)speed values until the processing logic identifies a set of speed values(e.g., fuel efficient speed values) that provide an optimized (e.g.,best) fuel economy (e.g., least amount of fuel used) for the route whilestill meeting the threshold arrival time and meeting maximum thresholdspeed values and minimum threshold speed values (e.g., not exceedingmaximum regulatory speed value, not exceeding a maximum traffic speedvalue, not exceeding a maximum weather speed value, not being less thana minimum regulatory speed value, etc.). The processing logic maygenerate a speed profile reflecting the speed value (e.g., fuelefficient speed value) for each of the segments (e.g., similar to block320 of method 300). The processing logic may adjust change in speedbetween segments in the speed profile to meet a threshold speeddifference value (e.g., similar to block 322 of method 300).

FIG. 4 depicts a block diagram of an example computer device 400 withinwhich a set of instructions, for causing the machine to perform any ofthe one or more methodologies discussed herein can be executed, inaccordance with some implementations of the disclosure. Example computerdevice 400 can be connected to other computer devices in a LAN, anintranet, an extranet, and/or the Internet. Computer device 400 canoperate in the capacity of a server in a client-server networkenvironment. Computer device 400 can be a personal computer (PC), aset-top box (STB), a server, a network router, switch or bridge, or anydevice capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that device. Further,while only a single example computer device is illustrated, the term“computer” includes any collection of computers that individually orjointly execute a set (or multiple sets) of instructions to perform anyone or more of the methods discussed herein. In some implementations,the computer device 400 is AV server 150. In some implementations, theAV 101 includes computer device 400 (e.g., AVCS 140 is computer device400). In some implementations, computer device 400 executes thefuel-economy optimization module 142.

Example computer device 400 can include a processing device 402 (alsoreferred to as a processor or CPU), which can include processing logic403, a main memory 404 (e.g., read-only memory (ROM), flash memory,dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM),etc.), a static memory 406 (e.g., flash memory, static random accessmemory (SRAM), etc.), and a secondary memory (e.g., a data storagedevice 418), which can communicate with each other via a bus 430.

Processing device 402 represents one or more general-purpose processingdevices such as a microprocessor, central processing unit, or the like.More particularly, processing device 402 can be a complex instructionset computing (CISC) microprocessor, reduced instruction set computing(RISC) microprocessor, very long instruction word (VLIW) microprocessor,processor implementing other instruction sets, or processorsimplementing a combination of instruction sets. Processing device 402can also be one or more special-purpose processing devices such as anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA), a digital signal processor (DSP), network processor,or the like. In accordance with one or more aspects of the disclosure,processing device 402 can be configured to execute instructionsperforming any of the operations performed by fuel-economy optimizationmodule 142.

Example computer device 400 can further comprise a network interfacedevice 408, which can be communicatively coupled to a network 420.Example computer device 400 can further comprise a video display 410(e.g., a liquid crystal display (LCD), a touch screen, or a cathode raytube (CRT)), an alphanumeric input device 412 (e.g., a keyboard), acursor control device 414 (e.g., a mouse), and an acoustic signalgeneration device 416 (e.g., a speaker).

Data storage device 418 can include a computer-readable storage medium(or, more specifically, a non-transitory computer-readable storagemedium) 428 on which is stored one or more sets of executableinstructions 422. In accordance with one or more aspects of thedisclosure, executable instructions 422 can comprise executableinstructions to perform any of the operations of fuel-economyoptimization module 142.

Executable instructions 422 can also reside, completely or at leastpartially, within main memory 404 and/or within processing device 402during execution thereof by example computer device 400, main memory 404and processing device 402 also constituting computer-readable storagemedia. Executable instructions 422 can further be transmitted orreceived over a network via network interface device 408.

While the computer-readable storage medium 428 is shown in FIG. 4 as asingle medium, the term “computer-readable storage medium” should betaken to include a single medium or multiple media (e.g., a centralizedor distributed database, and/or associated caches and servers) thatstore the one or more sets of VM operating instructions. The term“computer-readable storage medium” includes any medium that is capableof storing or encoding a set of instructions for execution by themachine that cause the machine to perform any one or more of the methodsdescribed herein. The term “computer-readable storage medium” includes,but is not limited to, solid-state memories, and optical and magneticmedia.

Some portions of the preceding detailed descriptions have been presentedin terms of algorithms and symbolic representations of operations ondata bits within a computer memory. These algorithmic descriptions andrepresentations are the ways used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of operations leading to adesired result. The operations are those requiring physicalmanipulations of physical quantities. Usually, though not necessarily,these quantities take the form of electrical or magnetic signals capableof being stored, combined, compared, and otherwise manipulated. It hasproven convenient at times, principally for reasons of common usage, torefer to these signals as bits, values, elements, symbols, characters,terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. The disclosure canrefer to the action and processes of a computer system, or similarelectronic computing device, that manipulates and transforms datarepresented as physical (electronic) quantities within the computersystem's registers and memories into other data similarly represented asphysical quantities within the computer system memories or registers orother such information storage systems.

The disclosure also relates to an apparatus for performing theoperations herein. This apparatus can be specially constructed for theintended purposes, or it can include a general purpose computerselectively activated or reconfigured by a computer program stored inthe computer. Such a computer program can be stored in a computerreadable storage medium, such as, but not limited to, any type of diskincluding floppy disks, optical disks, CD-ROMs, and magnetic-opticaldisks, read-only memories (ROMs), random access memories (RAMs), EPROMs,EEPROMs, magnetic or optical cards, or any type of media suitable forstoring electronic instructions, each coupled to a computer system bus.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general purposesystems can be used with programs in accordance with the teachingsherein, or it can prove convenient to construct a more specializedapparatus to perform the method. The structure for a variety of thesesystems will appear as set forth in the description below. In addition,the disclosure is not described with reference to any particularprogramming language. It will be appreciated that a variety ofprogramming languages can be used to implement the teachings of thedisclosure as described herein.

The disclosure can be provided as a computer program product, orsoftware, that can include a machine-readable medium having storedthereon instructions, which can be used to program a computer system (orother electronic devices) to perform a process according to thedisclosure. A machine-readable medium includes any mechanism for storinginformation in a form readable by a machine (e.g., a computer). In someimplementations, a machine-readable (e.g., computer-readable) mediumincludes a machine (e.g., a computer) readable storage medium such as aread only memory (“ROM”), random access memory (“RAM”), magnetic diskstorage media, optical storage media, flash memory devices, etc. Thewords “example” or “exemplary” are used herein to mean serving as anexample, instance, or illustration. Any aspect or design describedherein as “example’ or “exemplary” is not necessarily to be construed aspreferred or advantageous over other aspects or designs. Rather, use ofthe words “example” or “exemplary” is intended to present concepts in aconcrete fashion. As used in this application, the term “or” is intendedto mean an inclusive “or” rather than an exclusive “or.” That is, unlessspecified otherwise, or clear from context, “X includes A or B” isintended to mean any of the natural inclusive permutations. That is, ifX includes A; X includes B; or X includes both A and B, then “X includesA or B” is satisfied under any of the foregoing instances. In addition,the articles “a” and “an” as used in this application and the appendedclaims may generally be construed to mean “one or more” unless specifiedotherwise or clear from context to be directed to a singular form.Moreover, use of the term “an embodiment,” “one embodiment,” “someembodiments,” “an implementation,” “one implementation,” “someimplementations,” or the like throughout may or may not mean the sameembodiment or implementation. One or more embodiments or implementationsdescribed herein may be combined in a particular embodiment orimplementation. The terms “first,” “second,” “third,” “fourth,” etc. asused herein are meant as labels to distinguish among different elementsand may not necessarily have an ordinal meaning according to theirnumerical designation.

In the foregoing specification, implementations of the disclosure havebeen described with reference to specific example implementationsthereof. It will be evident that various modifications can be madethereto without departing from the broader spirit and scope ofimplementations of the disclosure as set forth in the following claims.The specification and drawings are, accordingly, to be regarded in anillustrative sense rather than a restrictive sense.

What is claimed is:
 1. A method comprising: identifying route data for aroute for an autonomous vehicle (AV), the route data comprising athreshold arrival time of the AV arriving at a destination; determining,by a processing device based on fuel economy data associated with theAV, a fuel-efficient speed value for each of a plurality of segments ofthe route; calculating, based on the route data and the fuel-efficientspeed value for each of the plurality of segments of the route, anestimated arrival time of the AV arriving at the destination; andresponsive to the estimated arrival time of the AV arriving at thedestination not meeting the threshold arrival time of the AV arriving atthe destination: identifying, among the plurality of segments, at leasta subset of segments that each represent a candidate for speed increase;computing, for each segment in the subset and based on the fuel economydata, a correlation metric that indicates a correlation between a changein fuel economy and a change in speed for a corresponding segment in thesubset; and increasing, for at least one segment from the subset andbased on a respective correlation metric, a fuel-efficient speed valueof the corresponding segment from the subset to provide a speed profilereflecting the increased fuel-efficient speed value of the correspondingsegment, wherein the AV is to travel along the route based on the speedprofile.
 2. The method of claim 1, wherein the determining of thefuel-efficient speed value for each of the plurality of segmentscomprises: determining, based on regulatory speed limits and trafficdata, a minimum threshold speed value and a maximum threshold speedvalue for each of the plurality of segments of the route; obtaining,from the fuel economy data, the fuel-efficient speed value for each ofthe plurality of segments; and responsive to the fuel-efficient speedvalue of a respective segment of the plurality of segments not meeting acorresponding minimum threshold speed value or a corresponding maximumthreshold speed value, updating the fuel-efficient speed value for therespective segment to meet the corresponding minimum threshold speedvalue or the corresponding maximum threshold speed value.
 3. The methodof claim 1, wherein the fuel economy data comprises: one or more firstinput values comprising a first speed value; one or more first outputvalues comprising a first fuel economy value, the one or more firstoutput values resulting from one or more AVs driving in accordance withthe one or more first input values; one or more second input valuescomprising a second speed value; and one or more second output valuescomprising a second fuel economy value, the one or more second outputvalues resulting from the one or more AVs driving in accordance with theone or more second input values, wherein the change in fuel economy isbased on the first fuel economy value and the second fuel economy value,and wherein the change in speed is based on the first speed value andthe second speed value.
 4. The method of claim 3, wherein the one ormore first input values further comprise a first grade value, a firsttotal AV mass value, or a first wind value.
 5. The method of claim 1further comprising: receiving first sensor data associated with the AVdriving at a first speed value; determining, based on the first sensordata, a first fuel economy value; causing the fuel economy data to beupdated based on the first fuel economy value and the first speed value;and responsive to the first fuel economy value not being within athreshold range of fuel economy values associated with a plurality ofAVs driving at the first speed value, providing an alert.
 6. The methodof claim 1 further comprising: determining, based on regulatory speedlimits and traffic data, a plurality of minimum threshold speed valuesand a plurality of maximum threshold speed values for the route; anddividing, based on the plurality of minimum threshold speed values andthe plurality of maximum threshold speed values, the route into theplurality of segments, wherein each of the plurality of segments has acorresponding minimum threshold speed value and a corresponding maximumthreshold speed value that are substantially constant.
 7. The method ofclaim 1 further comprising: determining, based on regulatory speedlimits and traffic data, a maximum threshold speed value for each of theplurality of segments, wherein each of the at least a subset of segmentsis below a corresponding maximum threshold speed value.
 8. The method ofclaim 1, wherein the at least one segment from the subset has therespective correlation metric that indicates least decrease in fueleconomy compared to increase in speed.
 9. The method of claim 1 furthercomprising: determining, based on the speed profile, that a differencebetween a first fuel-efficient speed value of a first segment of theroute and a second fuel-efficient speed value of a subsequent segment ofthe route exceeds a threshold speed difference value; and adjustingchange in speed between the first segment and the subsequent segment inthe speed profile to meet the threshold speed difference value.
 10. Asystem comprising: a memory device; and a processing device, coupled tothe memory device, wherein the processing device is to: identify routedata for a route for an autonomous vehicle (AV), the route datacomprising a threshold arrival time of the AV arriving at a destination;determine, based on fuel economy data associated with the AV, afuel-efficient speed value for each of a plurality of segments of theroute; calculate, based on the route data and the fuel-efficient speedvalue for each of the plurality of segments of the route, an estimatedarrival time of the AV arriving at the destination; and responsive tothe estimated arrival time of the AV arriving at the destination notmeeting the threshold arrival time of the AV arriving at thedestination: identify, among the plurality of segments, at least asubset of segments that each represent a candidate for speed increase;compute, for each segment in the subset and based on the fuel economydata, a correlation metric that indicates a correlation between a changein fuel economy and a change in speed for a corresponding segment in thesubset; and increase, for at least one segment from the subset and basedon a respective correlation metric, a fuel-efficient speed value of thecorresponding segment from the subset to provide a speed profilereflecting the increased fuel-efficient speed value of the correspondingsegment, wherein the AV is to travel along the route based on the speedprofile.
 11. The system of claim 10, wherein to determine thefuel-efficient speed value for each of the plurality of segments, theprocessing device is to: determine, based on regulatory speed limits andtraffic data, a minimum threshold speed value and a maximum thresholdspeed value for each of the plurality of segments of the route; obtain,from the fuel economy data, the fuel-efficient speed value for each ofthe plurality of segments; and responsive to the fuel-efficient speedvalue of a respective segment of the plurality of segments not meeting acorresponding minimum threshold speed value or a corresponding maximumthreshold speed value, update the fuel-efficient speed value for therespective segment to meet the corresponding minimum threshold speedvalue or the corresponding maximum threshold speed value.
 12. The systemof claim 10, wherein the fuel economy data comprises: one or more firstinput values comprising a first speed value; one or more first outputvalues comprising a first fuel economy value, the one or more firstoutput values resulting from one or more AVs driving in accordance withthe one or more first input values; one or more second input valuescomprising a second speed value; and one or more second output valuescomprising a second fuel economy value, the one or more second outputvalues resulting from the one or more AVs driving in accordance with theone or more second input values, wherein the change in fuel economy isbased on the first fuel economy value and the second fuel economy value,and wherein the change in speed is based on the first speed value andthe second speed value.
 13. The system of claim 10, wherein theprocessing device is further to: receive first sensor data associatedwith the AV driving at a first speed value; determine, based on thefirst sensor data, a first fuel economy value; cause the fuel economydata to be updated based on the first fuel economy value and the firstspeed value; and responsive to the first fuel economy value not beingwithin a threshold range of fuel economy values associated with aplurality of AVs driving at the first speed value, provide an alert. 14.The system of claim 10, wherein the processing device is further to:determine, based on regulatory speed limits and traffic data, aplurality of minimum threshold speed values and a plurality of maximumthreshold speed values for the route; and divide, based on the pluralityof minimum threshold speed values and the plurality of maximum thresholdspeed values, the route into the plurality of segments, wherein each ofthe plurality of segments has a corresponding minimum threshold speedvalue and a corresponding maximum threshold speed value that aresubstantially constant.
 15. The system of claim 10, wherein theprocessing device is further to: determine, based on the speed profile,that a difference between a first fuel-efficient speed value of a firstsegment of the route and a second fuel-efficient speed value of asubsequent segment of the route exceeds a threshold speed differencevalue; and adjust change in speed between the first segment and thesubsequent segment in the speed profile to meet the threshold speeddifference value.
 16. A non-transitory computer-readable storage mediumhaving instructions stored thereon that, when executed by a processingdevice, cause the processing device to: identify route data for a routefor an autonomous vehicle (AV), the route data comprising a thresholdarrival time of the AV arriving at a destination; determine, based onfuel economy data associated with the AV, a fuel-efficient speed valuefor each of a plurality of segments of the route; calculate, based onthe route data and the fuel-efficient speed value for each of theplurality of segments of the route, an estimated arrival time of the AVarriving at the destination; and responsive to the estimated arrivaltime of the AV arriving at the destination not meeting the thresholdarrival time of the AV arriving at the destination: identify, among theplurality of segments, at least a subset of segments that each representa candidate for speed increase; compute, for each segment in the subsetand based on the fuel economy data, a correlation metric that indicatesa correlation between a change in fuel economy and a change in speed fora corresponding segment in the subset; and increase, for at least onesegment from the subset and based on a respective correlation metric, afuel-efficient speed value of the corresponding segment from the subsetto provide a speed profile reflecting the increased fuel-efficient speedvalue of the corresponding segment, wherein the AV is to travel alongthe route based on the speed profile.
 17. The non-transitorycomputer-readable storage medium of claim 16, wherein to determine thefuel-efficient speed value for each of the plurality of segments, theprocessing device is to: determine, based on regulatory speed limits andtraffic data, a minimum threshold speed value and a maximum thresholdspeed value for each of the plurality of segments of the route; obtain,from the fuel economy data, the fuel-efficient speed value for each ofthe plurality of segments; and responsive to the fuel-efficient speedvalue of a respective segment of the plurality of segments not meeting acorresponding minimum threshold speed value or a corresponding maximumthreshold speed value, update the fuel-efficient speed value for therespective segment to meet the corresponding minimum threshold speedvalue or the corresponding maximum threshold speed value.
 18. Thenon-transitory computer-readable storage medium of claim 16, wherein thefuel economy data comprises: one or more first input values comprising afirst speed value; one or more first output values comprising a firstfuel economy value, the one or more first output values resulting fromone or more AVs driving in accordance with the one or more first inputvalues; one or more second input values comprising a second speed value;and one or more second output values comprising a second fuel economyvalue, the one or more second output values resulting from the one ormore AVs driving in accordance with the one or more second input values,wherein the change in fuel economy is based on the first fuel economyvalue and the second fuel economy value, and wherein the change in speedis based on the first speed value and the second speed value.
 19. Thenon-transitory computer-readable storage medium of claim 16, wherein theprocessing device is further to: receive first sensor data associatedwith the AV driving at a first speed value; determine, based on thefirst sensor data, a first fuel economy value; cause the fuel economydata to be updated based on the first fuel economy value and the firstspeed value; and responsive to the first fuel economy value not beingwithin a threshold range of fuel economy values associated with aplurality of AVs driving at the first speed value, provide an alert. 20.The non-transitory computer-readable storage medium of claim 16, whereinthe processing device is further to: determine, based on regulatoryspeed limits and traffic data, a plurality of minimum threshold speedvalues and a plurality of maximum threshold speed values for the route;and divide, based on the plurality of minimum threshold speed values andthe plurality of maximum threshold speed values, the route into theplurality of segments, wherein each of the plurality of segments has acorresponding minimum threshold speed value and a corresponding maximumthreshold speed value that are substantially constant.